Logon Security Considerations - Screen Mapping

There are many ways a programmer can implement security. One important thing to remember with screen mapping is that the end-user is never on-line with the host system. The end-user has no way of interacting with the host system that you haven’t provided for. With this in mind, the following are a few examples of login security methods:

The developer can create a “Login” Transaction Macro that is linked to the Login Host Screen. If a new user needs to sign on, this can be accomplished through a simple call to the “Login” macro.

The user ID and password specified when the user logged in could be provided to the script. The login would occur when the user called the first macro.

A generic login could be specified, and the user changed dynamically using a system function such as “sign-on” or “change-to”. This command could be executed as part of a single Transaction Macro, or as a separate one called only when the user changes.